Repository navigation
open-cloud-mesh: receive shares from a real Nextcloud 35.0.1 (#138) - #256
Merged
Merged
Conversation
Spike against the official nextcloud:35.0.1-apache image: Nextcloud signs
RFC 9421 (tag="ocm") with an ES256 key, sends the legacy
`{name: webdav, options: {sharedSecret, permissions: "<prop>"}}` protocol
without a uri, puts the receiver's URL in `shareWith`, sends folders as
resourceType file, and leaves senderDomain out of SHARE_UNSHARED.
Plugin:
- accept the legacy protocol: fetch `<signer origin>/public.php/webdav/`
with Basic `<secret>:`, through a new fixed-path read operation
`fetch-legacy-webdav`, only on the origin the host verified;
- accept `bob@https://host` / `bob@http://host` addresses;
- senderDomain optional in notifications (must still be the signer);
- refuse an HTML answer for a non-HTML name (Nextcloud's folder page).
e2e:
- nextcloud.spec.ts (opt-in, OCM_NEXTCLOUD_E2E=1, Docker, loopback only):
Nextcloud shares a file through its own OCS API; the File arrives,
unsharing marks it unshared, a folder share is refused. Fails at the pin
a12b74a (host refuses ES256); passes on atomic-server branch
claude/plugin-ocm-es256 (4dd4f39be).
- shared install helpers (helpers.ts); peer.mjs shares its test CA across
parallel workers, since the server trusts exactly one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A spike and an opt-in e2e with the official
nextcloud:35.0.1-apacheimage, on loopback and Docker only, with invented data.What Nextcloud actually sends:
tag="ocm"signatures with an ES256 key.webdav/optionsshare protocol, with no uri.shareWithwith a scheme (bob@https://host).resourceType: file.senderDomain.Plugin changes:
<signer origin>/public.php/webdav/with Basic auth, through a new fixed-path read operation,fetch-legacy-webdav.user@https://hostaddresses.senderDomainis optional, but when present it must still be the signer.e2e:
e2e/nextcloud.spec.tsis skipped unlessOCM_NEXTCLOUD_E2E=1. Shared helpers moved toe2e/helpers.ts, andpeer.mjsshares its test CA between parallel workers.Results:
a12b74a, the Nextcloud spec fails: the host refuses the ES256 key with 401.claude/plugin-ocm-es256(4dd4f39be: ES256 JWKs plus a keyid-domain fallback; patch on Agent coordination board (Claude sessions: rules, status, hand-offs) #227), both specs pass.Refs #138. The issue stays open until a pin includes the host fix and the opt-in e2e passes at the pin.
🤖 Generated with Claude Code